Skip to main content

GSTIN Details Retrieval API

The following document highlights the details of the GSTIN Details Retrieval API.

API Description

Objective

The GSTIN Details Retrieval API queries the GSTIN portal and returns a GSTIN's registration status, taxpayer details, and financial activity data, including filing history, tax liability, and HSN information.

InputOutput
The GSTIN and flags indicating which details are requiredThe registration details, HSN data, branch details, and filing history associated with the GSTIN. A complete list of fields is provided under the Success Response Details section.

API URL

https://ind-engine.thomas.hyperverge.co/v1/GSTINDetailsRetrieval

API Endpoint

GSTINDetailsRetrieval

Overview

The GSTIN Details Retrieval API is RESTful and uses standard HTTP verbs and status codes. The responses are in JSON format and you should upload all images and files as form-data through a POST request.

Method - POST

Authentication

You need a unique pair of application ID (appId) and application key (appKey) from HyperVerge to verify your identity for accessing the GSTIN Details Retrieval API.

Headers

ParameterMandatory or OptionalDescriptionInput Format
content-typeMandatoryThe media type for the request payload.application/json
appIdMandatoryThe application identifier from HyperVerge. You can find the details in the dashboard's credentials tab.Unique value
appKeyMandatoryThe application key from HyperVerge. You can find the details in the dashboard's credentials tab.Unique value
transactionIdMandatoryA unique identifier for tracking a user journey.Unique value mapped to the user's journey

Inputs

The following table provides the complete information on the parameters used in the request body for the GSTIN Details Retrieval API:

ParameterMandatory or OptionalTypeDescriptionInput FormatDefault Value
gstinMandatoryStringThe Goods and Services Tax Identification Number (GSTIN) of the user.15-character alphanumeric stringNot Applicable
hsnDetailsMandatoryStringIndicates whether HSN (Harmonized System of Nomenclature) details are required in the response.true or falseNot Applicable
branchDetailsMandatoryStringIndicates whether branch details are required in the response.true or falseNot Applicable
filingDetailsMandatoryStringIndicates whether filing details are required in the response.true or falseNot Applicable
liabilityPaidDetailsMandatoryStringIndicates whether liability paid details are required in the response.true or falseNot Applicable

Request

The following section shows the standard curl request for the GSTIN Details Retrieval API.

curl --location --request POST 'https://ind-engine.thomas.hyperverge.co/v1/GSTINDetailsRetrieval' \
--header 'Content-Type: application/json' \
--header 'appId: <Enter_the_App_ID>' \
--header 'appKey: <Enter_the_App_Key>' \
--header 'transactionId: <Enter_the_Transaction_ID>' \
--data '{
"gstin": "<Enter_the_GSTIN>",
"hsnDetails": "<Enter_true_or_false>",
"branchDetails": "<Enter_true_or_false>",
"filingDetails": "<Enter_true_or_false>",
"liabilityPaidDetails": "<Enter_true_or_false>"
}'

Success Response

The following is a sample response from the GSTIN Details Retrieval API when all detail flags are set to true:

{
"status": "success",
"statusCode": "200",
"result": {
"basicDetails": {
"gstin": "<GSTIN>",
"ekycFlag": "<eKYC_Flag>",
"compositionRate": "<Composition_Rate>",
"percentTaxInCash": "<Percent_Tax_In_Cash>",
"aggreTurnOverFY": "<Aggregate_Turnover_Financial_Year>",
"registrationType": "<Registration_Type>",
"aggreTurnOver": "<Aggregate_Turnover>",
"businessNature": [
"<Business_Nature_1>",
"<Business_Nature_2>"
],
"registrationDate": "<Registration_Date>",
"registrationStatus": "<Registration_Status>",
"percentTaxInCashFY": "<Percent_Tax_In_Cash_FY>",
"memberDetails": [
"<Member_1>",
"<Member_2>"
],
"natureOfCoreBusinessActivity": "<Nature_Of_Core_Business_Activity>",
"aadhaarVerified": "<Aadhaar_Verified>",
"legalBusinessName": "<Legal_Business_Name>",
"constitutionOfBusiness": "<Constitution_Of_Business>",
"tradeName": "<Trade_Name>",
"centralJurisdiction": "<Central_Jurisdiction>",
"isEInvoiceMandated": "<Is_E_Invoice_Mandated>",
"stateJurisdiction": "<State_Jurisdiction>",
"cancellationDate": "<Cancellation_Date>",
"isEInvoiceOpted": "<Is_E_Invoice_Opted>"
},
"hsnDetails": {
"goods": null,
"services": [
{
"hsnCode": "<HSN_Code>",
"hsnDescription": "<HSN_Description>"
}
]
},
"branchDetails": {
"message": "<Message>",
"principalAddress": {
"address": "<Principal_Address>",
"natureOfBusiness": "<Nature_Of_Business>"
},
"additionalAddresses": []
},
"filingDetails": {
"filingStatus": [
[
{
"finYear": "<Financial_Year>",
"returnType": "<Return_Type>",
"returnPeriod": "<Return_Period>",
"modeOfFiling": "<Mode_Of_Filing>",
"dateOfFiling": "<Date_Of_Filing>"
}
]
]
}
}
}

Success Response Details

The following table provides the details of the fields in a success response:

ParameterTypeDescription
basicDetails.gstinStringThe GSTIN provided in the request.
basicDetails.legalBusinessNameStringThe legal name of the business as registered on the GSTIN portal.
basicDetails.tradeNameStringThe trade name of the business.
basicDetails.registrationStatusStringThe current registration status of the GSTIN, such as "Active" or "Cancelled".
basicDetails.registrationDateStringThe date on which the GSTIN was registered (DD/MM/YYYY).
basicDetails.cancellationDateStringThe date on which the GSTIN was cancelled, if applicable.
basicDetails.registrationTypeStringThe type of GST registration, such as "Regular" or "Composition".
basicDetails.constitutionOfBusinessStringThe legal constitution of the business, such as "Private Limited Company" or "Partnership".
basicDetails.businessNatureArrayThe nature of business activities associated with the GSTIN.
basicDetails.natureOfCoreBusinessActivityStringThe primary business activity of the entity.
basicDetails.centralJurisdictionStringThe central tax jurisdiction under which the GSTIN is registered.
basicDetails.stateJurisdictionStringThe state tax jurisdiction under which the GSTIN is registered.
basicDetails.aggreTurnOverStringThe aggregate turnover of the entity.
basicDetails.aggreTurnOverFYStringThe financial year corresponding to the aggregate turnover.
basicDetails.isEInvoiceMandatedStringIndicates whether e-invoicing is mandated for the entity.
basicDetails.isEInvoiceOptedStringIndicates whether the entity has opted into e-invoicing.
basicDetails.aadhaarVerifiedStringIndicates whether the Aadhaar of the business owner has been verified.
basicDetails.ekycFlagStringThe eKYC status of the entity.
basicDetails.memberDetailsArrayThe list of members associated with the entity.
hsnDetails.goodsArray / nullThe HSN codes and descriptions for goods traded by the entity. Returns null if no goods are registered. Returned only when hsnDetails is set to "true".
hsnDetails.servicesArrayThe HSN codes and descriptions for services provided by the entity. Returned only when hsnDetails is set to "true".
branchDetails.principalAddressObjectThe principal place of business address and its nature of business. Returned only when branchDetails is set to "true".
branchDetails.additionalAddressesArrayThe list of additional business addresses. Returned only when branchDetails is set to "true".
filingDetails.filingStatusArrayThe GST return filing history, including financial year, return type, return period, mode of filing, and date of filing. Returned only when filingDetails is set to "true".

Failure Response

The following is a sample response when the provided GSTIN is invalid or does not exist:

{
"statusCode": 400,
"status": "failure",
"error": "<Error_Message>",
"metaData": {
"requestId": "<Request_ID>",
"transactionId": "<Transaction_ID>"
}
}

Error Responses

The following are some error responses from the GSTIN Details Retrieval API:

{
"message": "Missing/Invalid credentials",
"statusCode": 401,
"status": "failure"
}

Error Response Details

An error response from the GSTIN Details Retrieval API contains a failure status with a relevant status code and error message. The following table lists all error responses:

Status CodeError MessageError DescriptionError Resolution
401Missing/Invalid credentialsThe request is missing the mandatory appId and appKey combination or has invalid values.Verify and provide valid credentials from the dashboard's credentials tab.
500Internal Server ErrorAn unexpected error occurred on the server.Check the request headers or contact the HyperVerge team for resolution.
Was this helpful?
Ask AIBeta
Hi! How can I help?
Ask me anything about HyperVerge products, APIs, and SDKs.
Try asking: